home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Linux Cubed Series 7: Sunsite
/
Linux Cubed Series 7 - Sunsite Vol 1.iso
/
system
/
serial
/
callback.001
/
callback~
/
callback
/
examples
/
callback.setup
next >
Wrap
Text File
|
1996-08-02
|
9KB
|
279 lines
############################################################################
# This file is part of the ICCE callback and dial-in monitoring system
# Copyright (c) 1994--1996, ICCE, State University of Groningen.
#
# This file demonstrates the setup for the callback mode of cb.
############################################################################
# The callback programs look for this file in the following order:
# 1. /etc/callback.setup
# 2. /usr/etc/callback.setup
# 3. /usr/local/etc/callback.setup
# As soon as one of these files is found, further searching stops.
#############################################################################
# The callback-mode setupfile consists of three sections:
# A general section in which directories etc. are determined
# A section where callback-destinations are defined
# A section where users are defined.
#
# These three sections must all be present, and must apppear in this order.
# First of all, determine the mode you want to use. In this file it's
# the callback mode.
# A mode MUST be specified:
mode: callback
# Next, specify the default modemline and possible other modem lines to use.
# If you have a single modem, set the default to this line.
# Otherwise select a particular modemline for your default, and name the
# other lines next.
# Whenever cb is called without a speficied line the default is used.
# At least a default line MUST be specified
line: ttyS2 ttyS1
# The default path where callback will find its mgetty-configuration molds.
# The default is BASE_PATH from the file configure.h
path: /conf/callback
# The log-file, on which messages from cb and cblogin are written.
# By default:
logfile: /var/adm/callback.log
# The dial-logfile, on which times and destinations of dial-out attempts
# are written. The format of the information written on the dial-logfile
# is given by the following examples:
#
# Sun Jul 23 23:20:00 1995
# calling Knarfix at 12345678 (cb V 4.10)
# Sun Jul 23 23:40:21 1995
# calling Phaedrix at 1234567 (login V 4.10)
#
# By default, dial-logging is done to /dev/null:
# diallogfile: /dev/null
# The panic logfile, used if the logfile somehow can't be opened.
# By default:
paniclog: /dev/console
# The verbosity of the logging: select between on, off, or default.
# off: only logging of grammatical errors in the setup-file,
# default: errors and warnings are logged
# on: errors, warnings and some process-monitoring is logged
# max: errors, warnings and extensive process-monitoring is logged
# By default:
log: default
# mgetty itself expects its files in a certain directory.
# By default (as used by the mgetty+sendfax software):
mgettyconfig: /usr/local/etc/mgetty+sendfax/mgetty.config
# The mgetty-process listening to a particular modem-line will be reached
# via a symbolic link. E.g., modem.ttyS1.
# The part WITHOUT the line-extension may be specified here. The callback
# software will add the '.<line>' suffix, coming up with something like
# /sbin/modem.ttyS2
# By default:
modemgetty: /sbin/modem
# The email-address is used in cblogin messages if set.
# By default: "root"
# A commented-out example:
#email: you@your.computer
# The login program. This program is used to overlay cblogin whenever a
# user is validated for callback.
# By default:
login: /bin/login
# The number of times callbacks are retried. After trying in vain for
# this number of times to connect with a particular phonemumber,
# callback stops trying to call it, and returns to its default (wait) state.
# By default:
retry: 3
# The number of seconds callbacks are retried. After trying in vain for
# this number of seconds to connect with a particular phonemumber,
# callback stops trying to call it, and returns to its default (wait) state.
# By default:
maxtime: 300
# There are two ways to force cb to call a remote connection:
# The short form is: cb User Destination
# The extensive form is: cb call User Destination.
# If you want to use 'cb call User Destination' rather than
# 'cb User Destination' uncomment 'call' below.
# By default the short form is used.
#call
# If you WANT phonenumbers to appear in the 'cb list' command, then
# uncomment the 'phonenumbers' entry.
# By default, numbers are NOT shown.
#phonenumbers
# If you WANT extra-destinations to appear in the list of destinations
# presented to the users of callback, uncomment the 'extra' entry.
# By default, the extra destinations are not displayed. The 'cb list' command
# will always display all destinations, regardless of the usage of 'extra' in
# this file.
#extra
# If you WANT direct-destinations to appear in the list of destinations
# presented to the users of callback, uncomment the 'direct' entry.
# By default, the direct destinations are not displayed. The 'cb list'
# command will always display all destinations, regardless of the usage
# of 'direct' in this file.
#direct
# If you DON'T normal destinations to appear in the list of destinations
# presented to the users of callback, uncomment the 'nodestinations' entry.
# By default, the normal destinations are not displayed. The 'cb list'
# command will always display all destinations, regardless of the usage
# of 'direct' in this file.
#nodestinations
#############################################################################
# The next section contains destinations. These are the computers that
# may be used for callback.
#
# Instead of a phonenumber, the entries
# direct
# and
# extra
# can also be used.
#
# 'Direct' allows the entry into the computer running callback, without
# being called back.
#
# 'Extra' allows the callback to whatever phonenumber. The particular
# phonenumber is requested at initial login-time.
#
# Every destination belongs to a group. Below, at the users section, users
# are associated with groups, rather than destinations.
# The groupname defines a set of destinations that may be requested by the
# particular user.
# The same destination can be used for multiple groups, but, in that case,
# no user can be part of both groups.
#
# The destinations start with the 'destinations:' keyword, to be followed
# by as many destinations are required.
#
# A destination is formed according to the following syntax:
#
# group : destinationname MODE
#
# MODE is either:
# extra (extra-callback destination)
# direct (for direct logins)
# <phonenumber> [using <filename>] (number plus optional file)
#
# A phonenumber may start with a *, and consists apart from that of digits
# and comma's: comma's indicate delays on Hayes-compatible modems.
#
# A filename is the path to a special configuration file which may be
# used with the particular destination.
#
# Some examples:
destinations:
d1: knarfix 123456
dest2: phaedrix 789012
spec: lunatix 0712396 using /conf/callback/callback.2400.ttyS2
local: xinix 1234
local: bambix 5678
ed: open direct
sm: its-me extra
# So, the groups d1, dest2, spec, local, ed and sm are defined. For
# each group one or more destinations to be called back are possible,
# e.g., 'knarfix' is the destination for group d1; the group 'local'
# has two destinations.
# The phonenumber to reach the destinations is given too: e.g., 123456 to
# reach knarfix.
# Note the group 'ed': when the destination 'open' is requested, direct
# entry is granted (no callback, but a username/password must still be
# provided.
# Also note the group 'sm': when the destination 'its-me' is requested, a
# phone number can be requested which will thereupon be the number called
# back.
###########################################################################
# The final section defines the users.
# The usersection starts with the
# users:
# keyword.
# Users are granted callback facilities to the destinations of the group(s)
# to which they belong.
# Multiple groups are possible, as long as no destination ambiguity
# results.
users:
frank: local, d1, sm
karel: spec, ed, local
# The user frank is allowed to use the groups 'local', 'd1', and 'its-me'.
# So, frank can be called back at knarfix, xinix, bambix, and can also
# request a callback to wherever,using the its-me extra callback line.
# The user karel is allowed callback to 'lunatix', using the special-modem
# setting file /conf/callback/callback.2400.ttyS2, and to xinix and bambix.
# Furthermore, karel can do a direct dial-in (no callback) using the pseudo
# callback destination 'open' (being the 'destination' of 'ed'.